Skip to content

[codex] Soften plugin signal verification#181

Merged
Pigbibi merged 1 commit into
mainfrom
codex/soften-plugin-signal-verify
Jun 18, 2026
Merged

[codex] Soften plugin signal verification#181
Pigbibi merged 1 commit into
mainfrom
codex/soften-plugin-signal-verify

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Keep Cloud Run plugin mount env verification strict.
  • Treat unreadable, missing, malformed, or schema-mismatched plugin signal files as warnings so strategy runtime can fall back to the base plan.
  • Prevent missing plugin signals from blocking strategy switch sync and scheduler updates.

Validation

  • python3 -m py_compile scripts/verify_cloud_run_strategy_plugin_mounts.py
  • Function-level check for unreadable signal path returning warning only

@Pigbibi Pigbibi merged commit f4a067e into main Jun 18, 2026
1 check passed
@Pigbibi Pigbibi deleted the codex/soften-plugin-signal-verify branch June 18, 2026 18:00

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 92fe7cf0f5

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +187 to 191
print(
f"Warning: {service}:{env_name} expected schema {expected_schema}, "
f"got {signal.get('schema_version')!r} at {signal_path}; "
"strategy runtime will ignore the plugin until it is fixed."
)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep schema mismatches blocking deploy

When a mount sets expected_schema_version and the artifact is otherwise valid JSON with the wrong schema, this now only warns and the workflow proceeds. I checked the runtime path wired in main.py (parse_strategy_plugin_mounts / load_configured_strategy_plugin_signals from the vendored quant_platform_kit), and that loader does not consume expected_schema_version, so it will not ignore the plugin as this message says; it can load an incompatible signal into strategy execution instead of falling back to the base plan.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant